Indicate whether the frequency plan is applicable to gateways #7235
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
References: TheThingsNetwork/lorawan-frequency-plans#41
Extended the
FrequencyPlanDescription
struct withGateways
field to indicate that the frequency plan is relevant for a gateway.Added
GatewaysOnly
flag to theListFrequencyPlans
RPC to filter out non-gateway related plans.Changes
FrequencyPlanDescription
struct withGateways
field to indicate that the frequency plan is relevant for a gatewayGatewaysOnly
flag to theListFrequencyPlans
RPC to filter out non-gateway related plansgateways-only
flag to thelist-frequency-plans
CLI command to filter out non-gateway related plansTesting
Steps
gateways-only
flag on thelist-frequency-plans
CLI command to filter out non-gateway related frequency plansResults
gateways
filed istrue
Regressions
Notes for Reviewers
Checklist
README.md
for the chosen target branch.CHANGELOG.md
.CONTRIBUTING.md
, there are no fixup commits left.